Method and system for omnichannel supervision

ABSTRACT

In one embodiment described herein, an omnichannel supervision interface system and method includes a hardware processor, and a graphics engine executed by the processor for displaying a first portion to display, for one contact center agent among a plurality of contact center agents, a near-real time transcript of the contact center agent&#39;s conversation with one customer over a plurality of channels, and a second portion to display a first media category of a session of the contact center agent and the customer, wherein the omnichannel supervision interface is operative to display a plurality of channels for the plurality of contact center agents. Related methods, apparatus, and systems are also described.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application No. 15/371,248,filed on Dec. 7, 2016, the content of which is incorporated herein byreference in its entirety.

TECHNICAL FIELD

The present disclosure generally relates to methods and systems for usein supervision of omnichannel systems for monitoring customer tobusiness support interactions.

BACKGROUND

Contact centers are typically busy places where service agents interactwith customer calls over a variety of channels, including, but notnecessarily limited to: chats, emails, and so forth, while supervisorsmonitor their progress and manage the volume of issues coming in acrossall channels. It is important for the work of service agents to bemonitored carefully and to be strategically thought-out, since everyinteraction with a customer costs the business money. Service agents canbe co-located together with their supervisor. Service agents can alsowork as remote employees, a model which is becoming more commonplace ascosts are often lower.

Although contact center supervisors serve a managerial role, they oftenfunction as mentors, motivators, managers, as well as service agents, ina task requiring supervisors to function as multitaskers as well. Theyoften lead teams of 10-20 agents, and must manage volume across allservice channels that are coming into the contact center. At any point,supervisors can be called upon to manage and coach agents, handle toughcustomers, adjust staff, prepare reports for management, all whileensuring service level and quality objectives are maintained.

Traditionally, supervisors monitor how agents are performing at theirjobs to make sure they are productive and working efficiently on all theissues coming in. This often includes looking to standard call centermetrics such as an agent's average handle time (AHT) or average speed toanswer (ASA), but there is a host of other data the supervisor can lookinto to get a sense of an agent's workload and performance. Supervisorsoften walk around the floor to get a sense for how things are going bywatching the agents and listening to conversations, while maintainingvisibility for agents to ask them questions as well. However, it can bedifficult to get that same feel for how an agent is doing when thesupervisor or agent is remote.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure will be understood and appreciated more fullyfrom the following detailed description, taken in conjunction with thedrawings in which:

FIG. 1 is a simplified pictorial illustration of an interface formonitoring and time lapse recording of multiple omnichannel sessionsconstructed and operative in accordance with an embodiment of thepresent disclosure;

FIG. 2 is a detail of the interface of FIG. 1, focusing on the videocolumn;

FIG. 3 is a detail of the interface of FIG. 1, focusing on the row ofone agent;

FIG. 4 is a simplified block diagram of the flow of data through thesystem of FIG. 1; and

FIG. 5 is a simplified flowchart of one method for implementing thesystem of FIG. 1.

DESCRIPTION OF EXAMPLE EMBODIMENTS Overview

An omnichannel supervision interface system and method is described. Theomnichannel supervision interface system and method includes a hardwareprocessor, and a graphics engine executed by the processor fordisplaying a first portion to display, for one contact center agentamong a plurality of contact center agents, a near-real time transcriptof the contact center agent's conversation with one customer over aplurality of channels, and a second portion to display a first mediacategory of a session of the contact center agent and the customer,wherein the omnichannel supervision interface is operative to display aplurality of channels for the plurality of contact center agents.Related methods, apparatus, and systems are also described.

Exemplary Embodiment

Reference is now made to FIG. 1, which is a simplified pictorialillustration of an interface 100 for monitoring and time lapse recordingof multiple omnichannel sessions constructed and operative in accordancewith an embodiment of the present disclosure. In a typical omnichannelcontact center, supervisors may want access to real-time views of whichagents are working, which customers are waiting to be served, and whatwork is in progress in order to monitor performance and proactively takeinformed action to resolve issues. These issues may include bottlenecksor over-saturated queues for example, that cause customers to sufferlong wait times, and it's often up to the supervisor to adjust staff orshift priorities in such situations. It is appreciated that the term“customer” is used herein throughout to refer to a consumer of theservices provided by the omnichannel contact center. Other terms may beused as well to refer to a consumer, depending on context. For example,a customer executing a voice call may be referred to as a “caller”, or acustomer who has executed a chat may be referred to as a “chatter”.Other terms may be used as well in their appropriate context, as will beappreciated.

Often there is a need for supervisory monitoring either for compliance,coaching, or for quality reasons. FIG. 1 depicts an interface 100 whichis designed to enable monitoring and recording multipleinteractions—i.e. interactions of multiple agents 110A-110F. Theinterface 100 also provides for monitoring multiple channels. In thedepiction of FIG. 1, columns for video 120, voice 130, co-browsing 140(i.e., both the customer and the service agent see the same browser,typically enabled by using screen sharing software), chat 150, and feedsfrom Internet of Things (IoT) 160 enabled devices are shown. Otherchannels, including, but not limited to screen sharing may also bedisplayed in other columns. All of the above are displayed on theinterface 100 simultaneously in real-time or near-real-time fashion.

In addition to being displayed on the interface 100 as described above,the information presently displayed on the interface 100 is also storedfor retrieval and analysis at a later time. A first set of controls 170is available to enable viewing information and events displayed in theinterface 100 as a whole, and a set of controls 180A-180F is alsoprovided on a per agent basis for each of the multiple agents 110A-110F,enabling viewing information and events for each individual agent of themultiple agents 110A-110F. The controls are depicted as being thestandard symbols used according to IEC 60417—Graphical Symbols for Useon Equipment. These controls enable viewing the stored information in atime lapse fashion, where the information can be viewed on the interfaceat a speed faster or slower than the original capture rate of theinformation.

The information displayed is captured is across channels (e.g.,voice/video/chat/screen capture etc.) for a particular user to supportexpert interaction. The retrieval or playback is assembled and displayedin a seamless way such that if the interaction started with a text chat,the text chat is displayed first, and an ensuing video call is thendisplayed. A session may be played back in a complete fashion, enablingfast forwarding or rewinding during the playback, using the controls180A-180F. Key words may be highlighted during playback as will bedescribed below with reference to FIG. 2.

It is appreciated that the interface 100 events as they unfold acrossall channels of the displayed omnichannels. Additionally, the interfaceenables time lapse recording of these events, and at a later time,playback of the time lapse recording may be performed at the same timefor many of the channels or all of the channels. In that a supervisormay need to monitor a large number of agents, such as the multipleagents 110A-110F, and follow their interactions over a large number ofchannels, corresponding to the various columns, e.g. video 120, voice130, co-browse 40, chat 150, etc.), the interface 100 provides a systemwhich may help the supervisor perform his or her job. Additionally, theinterface 100 may comprise a machine learning sub-system which, overtime, will improve at detecting and isolating areas for the supervisorto focus on. The interface 100 may then bring these areas to theattention of the supervisor.

The machine learning sub-system may be used both in real time, in orderto detect a potential problem, and then to send a notification to thesupervisor, or, alternatively, in reviewing interactions in an off-line,non-real time fashion, to spot interactions where the supervisor'sintervention should have occurred, or where additional follow-up may benecessary on the part of the supervisor (whether in the form of agenttraining or in the form of contact with a customer). In that there maybe a large volume of customer interactions handled by the omnichannelcontact center, it may not be possible to review each interactionindividually in its entirety in order to isolate problem areas. Themachine learning sub-system (and its associated processing unit) enablesoff-line location and identification of such problem areas. The machinelearning sub-system may also prioritize the problematic interactions forwhich are to be reviewed.

Although not depicted, the interface 100 might also display a timer foreach ongoing interaction between an Agent and a customer. A conversationthat goes beyond a limit/threshold from average talk time will beflagged for further attention by the supervisor. The flagging willtypically be executed by a rule engine (described below, with referenceto FIG. 4). During omnichannel conversation, it is important to note thetotal time for resolution from start to end, and this time may includetime spent engaged in offline conversations like email or SMS. Totaltime of resolution and number of contacts before resolution is animportant parameter that gets tracked and linked directly to customersatisfaction. Information about timing may be performed by theomnichannel system so that supervisors can, if needed, take actions innear real time.

Exemplary detailed descriptions of each monitored channel will beprovided in the following discussions.

Reference is now made to FIG. 2, which is a detail 200 of the interface100 of FIG. 1, focusing on the video column 120. Focusing on the videocolumn 120 grid of Agent Sally 110A, a customer video 210 A is seen.Agent Sally's video 220A is also seen, as a small video display, inaddition to the customer video 210 A. A transcript 230 is also providedof the conversation between the customer, displayed by customer video210 A and Agent Sally's video 220A. The transcript 230 show ahighlighted word 240, depicted as a rectangle around a word, “plugged”.The highlighted word 240 is a keyword which is highlighted as part ofthe transcription routine.

Similarly, Agent Tom's video 210 is displayed, in this case, it is AgentTom 110B himself shown, and the customer's video 220B which appears asthe smaller video image. In either of the cases of the two videodisplays, 210A and 210B, it is the active member of the video sessionwhose video image 210A, 210B is displayed in the larger display, whilethe listening member of the video session whose video image 220A, 220Bis displayed in the smaller display. At present, the transcript 250 ofthe conversation between Agent Tom 110B and a customer receiving helpfrom Agent Tom 110B is not showing any highlighted keywords. In someembodiments, tagging might also be implemented. For example, if the callcenter agent is discussing (regardless of the channel) a refrigerator,then the tag “refrigerator” might be automatically applied to theconversation.

Agent Liz 110C is indicated as being ready 270 to receive a call fromthe next customer to the call center. By contrast, Agent Rick 110D isindicated as not being ready 270 to receive a call. This might bebecause Agent Rick 110D is on a break or not at his desk at present.

As can be seen in the above description of FIG. 2, any individual canmonitor and record multiple interaction sessions with multiple mediatypes or channel types. FIG. 2 depicted the ability to monitor multipleinteraction sessions for video. The depiction of FIG. 2 illustrates howthe omnichannel support center supervisor can monitor multiple videosessions at one time.

Reference is now made to FIG. 3, which is a detail 300 of the interfaceof FIG. 1, focusing on the row of one agent, in this particularinstance, and by way of example, Agent Sally 110A. Similar to what wasdiscussed above about FIG. 2, FIG. 3 depicts how multiple other channelsbesides video (the video column is omitted from FIG. 3, for ease ofdepiction) may be displayed for monitoring at one time. As with video,in the voice column, a live transcript appears, showing several keywords320, depicted with rectangles around them, for emphasis. One repeatedkeyword, multiple times, might serve as a flag to the supervisor thatimmediate attention or intervention is called for. For example, repeateduse of profanity might be flagged (possibly in a red font, or in boldletters, or some other manner, as is known in the art). Similarly, ifthe customer were to repeatedly use the same keyword, e.g. “Cloud . . .cloud . . . cloud . . . ”, might serve as a flag to the supervisor thatsupervisory attention might be called for. The chat window might alsohave a tag sub-window 330, where tags (i.e. a displaying of metadatawhich might help to describe the subject of the voice (or video)session) are automatically applied. For example, tags might includetopics of conversation, such as “Fridge” or “Noise”.

The Co-browse column enables displaying a screen from the Agent'smonitor and/or the a screen from customer's monitor 340. The Chat column150 might function similarly to the video transcripts 230, 250 displayedfor the video column 120 (FIG. 2) and the voice transcript 310 displayedfor the voice column 130. That is to say that live chat keywords andtags 350 might appear in the chat column 150.

Tags can be added to a tagging system (not depicted) by systemadministrators. At a later time, when a chat or a transcript appears inthe appropriate location in the interface 100 (i.e. the chat columns150, the transcript 230, etc., the system would then highlight keywords.Additionally, the system might display, for each tagged word, a numberof times the word was spoken or mentioned in the conversation. Thesystem can use a rule engine (described below with reference to FIG. 4),and monitor if a specific word is repeated too many times based on athreshold, and then start tracking the conversation as an interestingevent in timeline and time lapse recording. As such, the system is ableto create static tags but may then learn tags, via the machine learningsub-system and automatically adjust the administrator list of tags in adynamic manner. In some embodiments, body language, gestures, andintegrated machine learning and video analytics can trigger events andmark them in a timeline for either one or both of time lapse recordingand/or real-time monitoring.

The IoT Channel column 160 may provide emails or other information madeavailable by IoT devices in the possession of the customer. In keepingwith the refrigerator example provided earlier (e.g. the tag “Fridge” intag sub-window 330), if the refrigerator were an IoT enabled device (or“thing”), then IoT messages (e.g. error messages, etc.) may be routed tothe call center agent, i.e. Agent Sally 110A. Such IoT messages wouldthen also appear in the interface 100 (FIG. 1), in the IoT messagewindow 360.

In that real time monitoring of multiple agents is typically difficultfor one supervisor, the interface 100 also enables monitoring callduration, which is easier to monitor in real time. If a session with acustomer is going on for what may be deemed a long time (e.g. longerthan a given threshold, which may vary for different products), thesupervisor may engage in more active monitoring or intervention.

Reference is now made to FIG. 4, which is a simplified block diagram 400of the flow of data through the system of FIG. 1. As noted above, thereare several types of feeds which may be input into the system of FIG. 1.Referring, for example, to FIG. 1, Video 120, Voice 130, Co-Browsing140, Chat 150, and IoT Channels 160 have already been discussed as“channels”. It is appreciated, however, that “Channels” of communicationare also feeds of data. The data flowing through the system of FIG. 1 isnow discussed.

Some feeds 410, such as Video 120, Voice 130, Co-Browsing 140, Chat 150,may be input directly for processing by a rule engine 420. As is knownin the art, a rule engine, such as rule engine 420, is a software systemwhich executes one or more rules in a runtime production environment.Rules engines, such as rule engine 420, may be acquired, by way ofexample, as a ready-made product, or alternatively a custom made rulesengine may be implemented in some embodiments.

Some feeds, however, may need preprocessing prior to being input intothe rule engine 420. An indirect feed 430, by way of example, but notlimited to an IoT feed, may require preprocessing by a processor 440prior to being input to the rule engine 420. The processor 440 may be anIFTTT (“If This Then That”) gateway, which is operating like aprocessor. As persons of skill in the art will appreciate, IFTTT is aweb-based service that allows users to create chains of conditionalstatements which may be triggered based changes to some other web basedservice. So, by way of a non-limiting example, if customer contacts acall center about a refrigerator problem, and the call center agent runsdiagnostics via the refrigerator's IoT interface, the results of thediagnostics may then be forwarded by the IFTTT gateway to the customerservice agent and/or to the rule engine 420.

The rule engine 420 may operate as a general purpose engine which mayalso operate like a SQL (standard query language) engine. However,instead of acting on database data, the rule engine 420 may act uponincoming data from the feed 410 and processor 440. The rule engine 420would output events which are relevant for display on the interface 100(FIG. 1), such as IoT data, customer call information, and so forth. Therule engine 420 also dynamically evaluates incoming metadata in order toperform filtering of events which are associated with the metadata. Forexample, if there are certain keywords to be detected, then metadata forevents which have strings matching those keywords may invoke the rulesof the rule engine 420. Rules may also be adjusted dynamically based onpattern recognition and machine learning (as will be discussed below).

Once incoming events (i.e., events in the direct feed 410 and in thenon-direct feed 430) are filtered by the rule engine 420, then the flowof events are further processed by a work flow engine 450. The work flowengine 450 is, as is known in the art, an application which manages andmonitors the state of activities in a workflow. Work flow engines, suchas work flow engine 450, may be acquired, by way of example, as aready-made product, or alternatively a custom made work flow engine maybe implemented in some embodiments.

The work flow engine 450 processes its input events into differentstreams, utilizing triggers, conditions (such as: “choose between thisand that”) and then outputs an outcome and/or an action. An outcome fromthe work flow engine 450 would either effect the action by an automatedbot 460 based on pre-defined patterns determined by a patternrecognition system 470, or it would pass it on to a router engine 480 tobe handled by the supervisor.

The pattern recognition system 470, enabling machine learning 475, maybe situated in the system of FIG. 1 to receive an output from the workflow engine 450. The pattern recognition system 470, as is known in theart, executes machine learning that focuses on the recognition ofpatterns and regularities in data output by the work flow engine 450.The machine learning 475 result generated by the pattern recognitionsystem 470 is input to the rule engine 420 in order to refine the rulesused by the rule engine 420, so that data from the feeds 410, 430 may beprocessed by the rule engine 420 more efficiently going forward. Machinelearning may be used to analyze the traditionally ignored rich datastream of interactions. Such events and triggers can then be used inorder to have automated bots take an action, or to route the interactionto supervisors managing the team or, alternatively, managing certaintypes of events (e.g. there might be a manager who specializes inhandling interactions with irate customers).

As stated above, the goal of the system of FIG. 1 for supervisors is tofilter out noise (i.e., normal conversations) and pay attention toproblems that are detected and assisted by the system to handle multiplechannels (i.e., Video 120, Voice 130, Co-Browsing 140, and so forth),and multiple agents (i.e., 110A-110F) at the same time, all while thesupervisor is managing the conversations and the agents from a singlework station. Accordingly, the system will route a typical, “successful”session between a customer and an agent to the bot 460. As noted above,the bot 460 effects the actions resulting from outcomes of the workflowengine. A session in which a problem develops will, as explained below,be routed by router 480 to a supervisor 490.

Conversations which are not judged by the work flow engine 450 as being“normal” or “successful” conversations, but rather are deemed to requirea supervisor's attention, will be routed by the system of FIG. 1, by therouter 480 to a supervisor 490. It is appreciated that the router 480will determine which supervisor 490 is the appropriate supervisor toforward such a conversation to. By way of example, the metadata of agiven feed 410, 430 may include the name (or other identifyinginformation) of its associated support agent. The router 480 may, forexample, use a lookup table, and route conversations to the supervisorassociated with the support agent associated with the conversation beingforwarded.

The time lapse view supported by the interface 100 is the view of thetargeted events across all channels that are filtered through the workflow engine 450 and allows the supervisor 490 to zoom into relevantareas without full review of an entire recording.

Reference is now made to FIG. 5, which is a simplified flowchart of onemethod for implementing the system of FIG. 1. At step 510, a graphicsengine (not shown) and driver (not shown) displays on a first portion ofa display for one contact center agent among a plurality of contactcenter agents, a near-real time (i.e. subject to a time delay introducedby network and processing of data) transcript of the contact centeragent's conversation with one customer over a plurality of channels. Atstep 520, the graphics engine displays, on a second portion of thedisplay, a co-browsing session of the contact center agent and thecustomer. At step 530, the graphics engine displays, on a third portionof the display, IoT events for an IoT thing associated with thecustomer, wherein the omnichannel supervision interface displays aplurality of channels for the plurality of contact center agents.

It is appreciated that the graphics engine is typically disposed in acomputer at the omnichannel customer support center and enablesdisplaying the interface 100, as described herein above.

It is appreciated that software components of the present disclosuremay, if desired, be implemented in ROM (read only memory) form. Thesoftware components may, generally, be implemented in hardware, ifdesired, using conventional techniques. It is further appreciated thatthe software components may be instantiated, for example: as a computerprogram product or on a tangible medium. In some cases, it may bepossible to instantiate the software components as a signalinterpretable by an appropriate computer, although such an instantiationmay be excluded in certain embodiments of the present disclosure.

It is appreciated that various features of the disclosure which are, forclarity, described in the contexts of separate embodiments may also beprovided in combination in a single embodiment. Conversely, variousfeatures of the disclosure which are, for brevity, described in thecontext of a single embodiment may also be provided separately or in anysuitable subcombination.

It will be appreciated by persons skilled in the art that the presentdisclosure is not limited by what has been particularly shown anddescribed hereinabove. Rather the scope of the disclosure is defined bythe appended claims and equivalents thereof:

What is claimed is:
 1. An omnichannel supervision interface methodcomprising: displaying a matrix with first axis populated by identifiersfor a plurality of contact center agents and a second axis populated byidentifiers for a plurality of communication channels, the channelsincluding at least one audio channel and at least one text channel;receiving, for at least some of the plurality of contact center agents,conversations over at least some of the plurality of communicationchannels between the contact center agents and customers; transcribinginto text, in near real time, audio conversations that occur on theaudio channel; populating the displayed matrix in near real time withthe conversations, comprising: for each active text conversation with aparticular contact center agent over a particular text channel,populating a portion of the matrix corresponding to the particular textchannel and the particular contact center agent with the text of theactive text conversation; and for each active audio conversation with aparticular contact center agent over a particular audio channel,populating a portion of the matrix corresponding to the particular audiochannel and the particular contact center agent with the transcribedtext of the active audio conversation; wherein the omnichannelsupervision interface displays in near real time conversations over theplurality of channels for the plurality of contact center agents.
 2. Themethod of claim 1, wherein at least one of the at least one text channelis a chat channel.
 3. The method of claim 1, wherein at least one of theat least one audio channel is an audio only channel.
 4. The method ofclaim 1, wherein at least one of the at least one audio channel ischannel that carries video in combination with audio.
 5. The method ofclaim 1, further comprising highlighting or tagging predefined keywordsthat appear within the conversations of the populated matrix.
 6. Asystem for simultaneously monitoring activity, the system comprising: aprocessor; a non-transitory computer readable memory storinginstructions which when executed by the processor cause the system toperform operations, comprising: displaying in a matrix with first axispopulated by identifiers for a plurality of contact center agents and asecond axis populated by identifiers for a plurality of communicationchannels, the channels including at least one audio channel and one textchannel; receiving, for at least some of the plurality of contact centeragents, conversations over at least some of the plurality ofcommunication channels between the contact center agents and customers;transcribing into text, in near real time, audio conversations thatoccur on the audio channel; populating the displayed matrix in near realtime with the conversations, comprising: for each active textconversation over a particular text channel for a particular contactcenter agent, populating a portion of the matrix corresponding to theparticular text channel and the particular contact center agent with thetext of the active text conversation; and for each active audioconversation over a particular audio channel for a particular contactcenter agent, populating a portion of the matrix corresponding to theparticular audio channel and the particular contact center agent withthe transcribed text of the active audio conversation; wherein thematrix displays in near real time conversations over the plurality ofchannels for the plurality of contact center agents.
 7. The system ofclaim 6, wherein at least one of the at least one text channel is a chatchannel.
 8. The system of claim 6, wherein at least one of the at leastone audio channel is an audio only channel.
 9. The system of claim 6,wherein at least one of the at least one audio channel is channel thatcarries video in combination with audio.
 10. The system of claim 6,further comprising highlighting or tagging predefined keywords thatappear within the conversations of the populated matrix.
 11. Anon-transitory computer readable media storing instructions which whenexecuted by a system cause the system to perform operations, comprising:displaying a matrix with first axis populated by identifiers for aplurality of contact center agents and a second axis populated byidentifiers for a plurality of communication channels, the channelsincluding at least one audio channel and at least one text channel;receiving, for at least some of the plurality of contact center agents,conversations over at least some of the plurality of communicationchannels between the contact center agents and customers; transcribinginto text, in near real time, audio conversations that occur on theaudio channel; populating the displayed matrix in near real time withthe conversations, comprising: for each active text conversation with aparticular contact center agent over a particular text channel,populating a portion of the matrix corresponding to the particular textchannel and the particular contact center agent with the text of theactive text conversation; and for each active audio conversation with aparticular contact center agent over a particular audio channel,populating a portion of the matrix corresponding to the particular audiochannel and the particular contact center agent with the transcribedtext of the active audio conversation; wherein the matrix displays innear real time conversations over the plurality of channels for theplurality of contact center agents.
 12. The media of claim 11, whereinat least one of the at least one text channel is a chat channel.
 13. Themedia of claim 11, wherein at least one of the at least one audiochannel is an audio only channel.
 14. The media of claim 11, wherein atleast one of the at least one audio channel is channel that carriesvideo in combination with audio.
 15. The media of claim 11, furthercomprising highlighting or tagging predefined keywords that appearwithin the conversations of the populated matrix.